翻訳と辞書
Words near each other
・ Lightning in a Bottle
・ Lightning in religion
・ Lightning in the South
・ Lightning injuries
・ Lightning Jack
・ Lightning Lake
・ Lightning Lake (Minnesota)
・ Lightning Lord
・ Lightning Love
・ Lightning Love (band)
・ Lightning LS-218
・ Lightning Machine
・ Lightning machine
・ Lightning man triplefin
・ Lightning McQueen
Lightning Memory-Mapped Database
・ Lightning Motorcycle
・ Lightning MultiCom
・ Lightning Novices' Chase
・ Lightning on the Strings, Thunder on the Mic
・ Lightning Over Water
・ Lightning Peak
・ Lightning Peak (British Columbia)
・ Lightning Point
・ Lightning Racer
・ Lightning Raiders
・ Lightning Records
・ Lightning Ridge Airport
・ Lightning Ridge, New South Wales
・ Lightning River


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Lightning Memory-Mapped Database : ウィキペディア英語版
Lightning Memory-Mapped Database

Lightning Memory-Mapped Database (LMDB) is a software library that provides a high-performance embedded transactional database in the form of a key-value store. LMDB is written in C with API bindings for several programming languages. LMDB stores arbitrary key/data pairs as byte arrays, has a range-based search capability, supports multiple data items for a single key and has a special mode for appending records at the end of the database (MDB_APPEND) which gives a dramatic write performance increase over other similar stores.〔(LMDB Reference Guide ). Retrieved on 2014-10-19〕 LMDB is not a relational database but like Berkeley DB and other similar databases such as dbm is strictly a key-value store.
LMDB may also be used concurrently in a multi-threaded or multi-processing environment, with read performance scaling linearly by design. LMDB databases may have only one writer at a time, however unlike many similar key-value store databases, write transactions ''do not'' block readers, nor do readers block writers. LMDB is also unusual in that multiple applications on the same system may simultaneously open and use the same LMDB store, as a means to scale up performance. Also LMDB does not require a transaction log (thereby increasing write performance by not needing to write data twice) because it maintains data integrity inherently by design.
== History ==

LMDB's design was first discussed in a 2009 post to the OpenLDAP developer mailing list,〔(back-mdb - futures ). Retrieved on 2014-10-19〕 in the context of exploring solutions to the cache management difficulty caused by the project's dependence on Berkeley DB. A specific goal was to replace the multiple layers of configuration and caching inherent to Berkeley DB's design with a single, automatically managed cache under the control of the host operating system.
Development subsequently began, initially as a fork of a similar implementation from the OpenBSD ldapd project.〔(MDB: A Memory-Mapped Database and Backend for OpenLDAP ). Retrieved 2014-10-19〕 The first publicly available version appeared in the OpenLDAP source repository in June 2011.〔(First public version of MDB source code ). Retrieved 2014-10-19〕
The project was known as MDB until November 2012, after which it was renamed in order to avoid conflicts with existing software.〔(MDB renamed to LMDB ). Retrieved 2014-10-19〕

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Lightning Memory-Mapped Database」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.